Skip to content

Conversation

nikgraf
Copy link
Collaborator

@nikgraf nikgraf commented Jul 1, 2025

No description provided.

@nikgraf nikgraf merged commit 7a2f13a into main Jul 1, 2025
6 checks passed
@nikgraf nikgraf deleted the ng/typesync-improvements branch July 1, 2025 18:23
Comment on lines +377 to +382
onChange={(e) => {
createAppForm.setFieldValue(
'directory',
`./${pipe(e.target.value, EffectString.toLowerCase, EffectString.replaceAll(/\s/g, '-'))}`,
);
}}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not use the listeners object on the createAppForm.AppField? It has an onChange as well.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no objection to use listener

sadly I'm not familiar with the TypeSync codebase nor TanStack Forms. Is listeners recommended by Tanstack forms or are there other benefits?

return [importStatement, typeDefinitions].join('\n\n');
}

export function buildMappingFile(schema: Domain.InsertAppSchema) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many of the properties won't have knowledgeGraphId if it is a custom property. So I think we should filter out the properties where property.knowledgeGraphId is null, yeah?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

spot on, created an issue here #301

can you pick it up? otherwise I do it as soon as I resolved the other urgent tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants